home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20021006-20030409
/
000357_jrd@cc.usu.edu_Mon Mar 3 11:33:21 EST 2003.msg
< prev
next >
Wrap
Text File
|
2020-01-01
|
3KB
|
59 lines
Article: 14153 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!panix!bloom-beacon.mit.edu!newsfeed.stanford.edu!logbridge.uoregon.edu!xmission!news.cc.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MS-DOS Kermit
Message-ID: <jDVkY2L9V8dP@cc.usu.edu>
Date: 3 Mar 03 09:27:26 MDT
References: <20030301.1833.31585snz@aral.vorkosigan.co.uk> <b3utjk$6gj$1@blue.rahul.net>
Organization: Utah State University
Lines: 46
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:14153
In article <b3utjk$6gj$1@blue.rahul.net>, Doug Kaufman <dkaufman@rahul.net> writes:
> jrd@cc.usu.edu (Joe Doupnik) writes:
>
>>In article <b3u44e$uf4$1@blue.rahul.net>, Doug Kaufman <dkaufman@rahul.net> writes:
>>
>>> OpenSSL has been ported to DOS and the latest 0.9.7a compiles under
>>> DJGPP out of the box, but is dependent on the WATT-32 networking
>>> library. SSHDOS is also available for DOS (does not use OpenSSL)
>>> (sshdos.sourceforge.net). Perhaps one of these can be used as a
>>> starting point for anyone who wants to add a secure layer to MSKERMIT.
>>> I am not sure how much licensing conflicts will add to technical
>>> problems involved.
>>------
>> I just visited Sourceforge and snagged the sshdos source archive
>>for a look-see. It's not the kind of thing which fits well with MSK. MSK
>>has no external libraries, no vendor libraries, no wattcp, and so on, and
>>it is for 16-bit real mode only. That also means all supporting material
>>is within MSK in open source form. Adding SSH would be quite a bit of work.
>> Licensing is definitely an issue. No GPL, no vendor licenses.
>
> I understand that this wouldn't be easy. I don't think I have the
> skills to do it myself. I believe that the TCP module in MSKERMIT and
> the WATT-32 libraries come from the same origin, but have diverged
> substantially over the years, with both originating from work by
> Erick Engelke. I doubt that SSH could be added in a 16-bit realmode
That's correct. The divergence is very large, too large to assume
one is like the other today. Also, the TCP code in MSK isn't in the form
of a library.
> program. The memory restrictions shouldn't be a problem if MSKERMIT
> were converted to a 32-bit protected mode program. Perhaps someone with
That's a rather massive change, I'm afraid. The environment is
no longer DOS and very few folks want to mess with DOS extenders needed
to deal with this. MSK already deals with expanded and extended memory
when available but it does not put code up there. If someone wants to give
it a try, go ahead.
Joe D.
> the necessary skills, time, and inclination will tackle the project.
> MSKERMIT is still the best available telnet client for DOS.
> Doug
> --
> Doug Kaufman
> Internet: dkaufman@rahul.net